5.1. Contacts

The following set of tests verifies that basic synchronization of contact information can be accomplished. In particular they attempt to verify the following:

that Contacts can be created, modified, and deleted on the device or server and that appropriate mappings are maintained to verify that there is no corruption or loss of data.
that special characters and multi byte characters can be correctly handled

Test ID	Objective	Procedure	Expected Result
7.1 Create new contact with minimal fields from the server	To verify that the fields that are already supported for a device are correctly transferred from server to device upon creation and from device to server upon modification.	Create a new contact entry from the server with all fields (except for addresses, emails, telephone numbers, and URLs) Perform a synchronization Modify it from the device, and then synchronize again.	The address book entry created on the server should be reflected on the device with an appropriate mapping of fields taking advantage of what the device supports. After modifying the entry and synchronizing, the modified entry is similar on both the device and server. The mappings used to send data to the devices should be the same on data returning to the server so that the expected fields are modified.
7.2 Create new contact with minimal fields from the device	To verify that the fields that are already supported for a device are correctly transferred from device to server upon creation and from device to server upon modification.	Create a new contact entry from the device with all fields filled out (except for addresses, emails, telephone numbers, and URLs) Perform a synchronization Modify it from the server, and then synchronize again.	The address book entry created on the device should be reflected on the server with an appropriate mapping of fields taking advantage of what the server supports After modifying the entry and synchronizing, the modified entry is similar on both the device and server. The mappings used to send data to the server should be the same on data returning to the device so that the expected fields are modified.
7.3 Special Characters	Verify that special characters in contacts correctly synchronize to and from the device.	From the Server, create a contact filling out all text fields with special characters. Perform a synchronization From the device modify the contact. Perform a synchronization Repeat creating contact on device and modifying on the server.	The contact should display on the device with all fields on the server correctly mapped to corresponding fields on the device. All special characters should correctly display on the device as it is displayed on the server. After modifying the contact, the characters should remain correctly displayed on both the device and server and the changes made on the device should be reflected on the server
7.4 Multi-Byte Characters	Verify that multi-byte characters in contacts correctly synchronize to and from the device.	From the server, create a contact filling out all text fields with multi-byte characters. Perform a synchronization From the device modify the contact Perform a synchronization Repeat creating contact on device and modifying on the server.	The contact should display on the device with all multi-byte characters correctly displayed. After modifying the contact, the multi-byte characters should remain correctly displayed on both the device and server, and the changes made on the device should be reflected on the server.
7.5 Delete a contact from the server	To verify that when a contact is deleted on the server, it is also deleted on the device.	From the server, delete an existing contact entry and synchronize.	The corresponding address book entry is removed from the device.
7.6 Delete a contact from the device	To verify that when a contact is deleted on the device, it is also deleted on the server.	From the device, delete an existing contact entry and synchronize	The corresponding address book entry is removed from the server.